Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 29 minutes and 41 seconds.Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1f9f585b26
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| const distanceFromBottom = container.scrollHeight - container.scrollTop - container.clientHeight; | ||
|
|
||
| if (distanceFromBottom <= BOTTOM_PROXIMITY_THRESHOLD) { | ||
| const rafId = requestAnimationFrame(() => { |
There was a problem hiding this comment.
The auto-scroll gate now computes distanceFromBottom only after submittedMessages.length has already increased, so users who were exactly at the bottom can still fail the <= 80 check when a newly received message is taller than 80px (e.g., long text or image). In that case, the view stops following new messages even though the user never scrolled up, which regresses expected chat behavior for active conversations.
Useful? React with 👍 / 👎.
1 participant
변경 배경
채팅 상세 페이지(
mentor/chat/[chatId]) 진입 시 초기 화면이 상단에서 시작되어 최신 메시지를 바로 확인하기 어려운 문제가 있었습니다.변경 내용
useChatListHandler에 스크롤 제어 상태 추가scrollContainerRefhasInitialAutoScrolledRefprevMessageCountRefisFetchingNextPage의존 단일 자동 스크롤 이펙트 제거chatId변경 시 자동 스크롤 상태 초기화overflow-y-auto)에scrollContainerRef연결기대 효과
참고
현재 실행 환경에
pnpm/corepack/npm실행 파일이 없어 CI 명령(lint/typecheck/build)은 로컬에서 실행하지 못했습니다.